Techniques for selectively reducing power levels of ports and core switch logic in infiniband switches

ABSTRACT

Methods for performing power management of InfiniBand (IB) switches and apparatus and software configured to implement the methods. Power management datagrams (MADs) are used to inform IB switches that host servers connected to the IB switch&#39;s ports are to transition to a reduced-power or offline state or have returned to a normal operating state. A subnet management agent (SMA) on the IB switch receives the power MADs from the host servers and tracks each server&#39;s operating state. In response to power down MADs, the SMA coordinates power reduction of the switch&#39;s ports and other switch circuitry. For switches with multi-port IB interfaces, a multi-port interface is caused to enter a reduced-power state when all of its ports are connected to host servers that are idle or offline. Additionally, when all of a switch&#39;s ports are connected to idle or offline servers the SMA may put the switch&#39;s core switch logic into a reduced-power state. Power MADs are also used to inform upstream IB switches when a switch is to transition to a reduced power state or has returned to a normal operating state.

BACKGROUND INFORMATION

Ever since the introduction of the microprocessor, computer systems havebeen getting faster and faster. In approximate accordance with Moore'slaw (based on Intel® Corporation co-founder Gordon Moore's 1965publication predicting the number of transistors on integrated circuitsto double every two years), the speed increase has shot upward at afairly even rate for nearly three decades. At the same time, the size ofboth memory and non-volatile storage has also steadily increased, suchthat many of today's personal computers are more powerful thansupercomputers from just 10-15 years ago. In addition, the speed ofnetwork communications has likewise seen astronomical increases.

Increases in processor speeds, memory, storage, and network bandwidthtechnologies have resulted in the build-out and deployment of networkswith ever increasing capacities. More recently, the introduction ofcloud-based services, such as those provided by Amazon (e.g., AmazonElastic Compute Cloud (EC2) and Simple Storage Service (S3)) andMicrosoft (e.g., Azure and Office 365) has resulted in additionalnetwork build-out for public network infrastructure, in addition to thedeployment of massive data centers to support these services that employprivate network infrastructure.

Cloud-based services are typically facilitated by a large number ofinterconnected high-speed servers, with host facilities commonlyreferred to as server “farms” or data centers. These server farms anddata centers typically comprise a large-to-massive array of rack and/orblade servers housed in specially-designed facilities. Many of thelarger cloud-based services are hosted via multiple data centers thatare distributed across a geographical area, or even globally. Forexample, Microsoft Azure has multiple very large data centers in each ofthe United States, Europe, and Asia. Amazon employs co-located andseparate data centers for hosting its EC2 and AWS services, includingover a dozen AWS data centers in the US alone. Typically, data isreplicated across geographically disperse data centers to ensure fullservice availability in case all or a portion of a data center goes downin view of power failure/availability events (e.g., blackouts andbrownouts), weather events and other natural disasters, networkavailability issues (e.g., cutting or otherwise unavailability ofhigh-capacity optical cables), and for other reasons.

Of significant importance are power consumption and coolingconsiderations. Faster processors generally consume more power, and whensuch processors are closely packed in high-density server deployments,overall performance is often limited due to cooling requirements. Notonly due the processors and other components in the servers consume anincredible amount of power, significant additional power levels areconsumed for cooling purposes. As a result, one of the largest operatingcosts for data centers is power. While much improvement has been made inthe form of lower power-consuming silicon, better cooling management,and smart power supplies, hardware vendors are quickly hitting a wallfor reducing energy costs.

Another aspect of data centers is scalability. As workloads increase anddecrease, servers are bought “on-line” and taken “off-line,” wherein anon-line server is available to service work requests while off-lineservers are unavailable to service work requests. Rather than shuttingoff-line servers completely down, these servers are typically put in areduced power state under which the server processors (the main powerconsumers) are put into a “sleep” or “sleeping” state (noting that someprocessors support multiple levels of reduced power states).

In recent years, network adapters and interfaces have been introducedthat also support reduced power states, such as some Ethernet adaptorsand InfiniBand (IB) Host Channel Adapters (HCAs). However, there arecurrently no mechanisms for reducing power states in InfiniBandswitches, whether by individual port or across an entire IB switch.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisinvention will become more readily appreciated as the same becomesbetter understood by reference to the following detailed description,when taken in conjunction with the accompanying drawings, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified:

FIG. 1 is a schematic drawing illustrating multiple servers connected toan InfiniBand switch via respective IB HCAs forming a sub-cluster;

FIG. 2 is a schematic diagram illustrating multiple sub-clustersconnected to an InfiniBand switch forming a cluster;

FIG. 3 is a flowchart illustrating operations and logic for reducing thepower state of IB components in connection with detection of changes inpower states to attached host servers, according to one embodiment;

FIG. 3a is a flowchart comprising an augmented version of the flowchartof FIG. 3 that is implemented for an InfiniBand switch employingmulti-port IB interfaces, according to one embodiment;

FIG. 4 is a flowchart illustrating operations and logic for returningthe power of applicable InfiniBand switch components and logic to anormal operating level in response to detection that an end-node (hostserver) has been returned to a normal operating state, according to oneembodiment;

FIG. 4a is a flowchart comprising an augmented version of the flowchartof FIG. 4 that is implemented for an InfiniBand switch employingmulti-port IB interfaces, according to one embodiment;

FIG. 5 is a schematic diagram illustrating an embodiment of apower-managed InfiniBand switch that is configured to support puttingindividual ports in reduced-power states, as well as putting theswitch's core logic in a reduced-power state;

FIG. 5a-5c show various power-state configurations of the power-managedInfiniBand switch of FIG. 5; wherein FIG. 5a shows a single port in areduced-power state; FIG. 5b shows all ports and the switch's core logicin a reduced-power state; and FIG. 5c shows two ports and the switch'score logic returning to a normal operation state;

FIG. 6 is a schematic diagram illustrating an embodiment of apower-managed InfiniBand switch including multi-port IB interfaces thatare configured to support putting individual ports and individualmulti-port IB interfaces in reduced-power states, as well as putting theswitch's core logic in a reduced-power state;

FIG. 6a-6d show various power-state configurations of the power-managedInfiniBand switch of FIG. 6; wherein FIG. 6a shows five ports in areduced-power state; FIG. 6b shows a multi-port switch in areduced-power state; FIG. 6c shows all multi-port IB interfaces and theswitch's core logic in a reduced-power state while a subnet managementagent and power management agent are in standby power states; and FIG.6d shows two ports and a multi-port switch and the switch's core logicreturning to a normal operation state;

FIG. 7 is a diagram illustrating the Management Datagram (MAD) baseformat defined by the InfiniBand Architecture Specification;

FIG. 8 is a diagram illustrating the Device Management MAD formatdefined by the InfiniBand Architecture Specification; and

FIG. 9 shows the link training state diagram defined by the InfiniBandArchitecture Specification.

DETAILED DESCRIPTION

Embodiments of methods for performing power management of InfiniBandswitches and apparatus and software for implementing the methods aredescribed herein. In the following description, numerous specificdetails are set forth to provide a thorough understanding of embodimentsdisclosed and illustrated herein. One skilled in the relevant art willrecognize, however, that the invention can be practiced without one ormore of the specific details, or with other methods, components,materials, etc. In other instances, well-known structures, materials, oroperations are not shown or described in detail to avoid obscuringaspects of the invention.

For clarity, individual components in the Figures herein may also bereferred to by their labels in the Figures, rather than by a particularreference number. Additionally, reference numbers referring to aparticular type of component (as opposed to a particular component) maybe shown with a reference number followed by “(typ)” meaning “typical.”It will be understood that the configuration of these components will betypical of similar components that may exist but are not shown in thedrawing Figures for simplicity and clarity or otherwise similarcomponents that are not labeled with separate reference numbers.Conversely, “(typ)” is not to be construed as meaning the component,element, etc. is typically used for its disclosed function, implement,purpose, etc.

FIG. 1 depicts a sub-cluster 100 of six servers 102 (labeled 102 a-102f), each of which is linked to an InfiniBand switch 104, wherein theservers links form a “star” configuration. In further detail, eachserver 102 includes an IB HCA 106 having a port linked in communicationwith a respective port 108 (labeled ‘P’) on IB switch 104 via arespective link 110. IB switch 112 further includes a subnet managementagent (SMA) 112. FIG. 2 illustrates a server cluster 200 comprising nsub-clusters 100 a-100 n having a similar configuration to sub-cluster100 of FIG. 1. The respective IB switches 104 a-104 n each include aport that is linked in communication to a corresponding port on an IBswitch 202 over a respective link 206 a-206 n. IB switch 202additionally includes an SMA 204.

Cluster 200 is illustrative of a cluster employing an IB switchhierarchy having two levels—one IB switch at the top level and n IBswitches at the second level. However, this is merely illustrative of ageneralized IB switch hierarchy architecture having m levels. Forillustrative purposes, embodiments disclosed herein are discussed in thecontent of a two-level IB switch hierarchy; however, it will beunderstood that the teachings and principles of these embodiments may beextended to an m level IB switch hierarchy.

Generally, servers 102 in an InfiniBand architecture are also referredto as “end-nodes,” while the links between the end-nodes and IBswitches, and between IB switches and other IB switches collectivelycomprise an IB fabric. A server including an IB HCA may also be referredto as an HCA host or host server.

In accordance with an aspect of some embodiments, techniques aredisclosed for selectively controlling the power state of individual IBswitch ports and associated circuitry, as well as entire IB switchesthemselves as a function of the power states of the HCA host serverslinked in communication with the IB switch ports (or optionally as afunction of the power states of the links and ports). FIG. 3 shows aflowchart 300 illustrating operations and logic for reducing the powerstate of IB components in connection with detection of changes in powerstates to host servers, according to one embodiment. As depicted bystart and end loop blocks 302 and 318, the operations and logic depictedbetween these block is implemented on an ongoing basis.

In a block 304, an end-node on the fabric (e.g., a server 102 includingan HCA 104) is idled as a result of a decrease in data center workloador for other reasons. This idle workload state is detected by theserver's operating system (OS), which is configured to put some or theserver's various components into a reduced power state. Generally, somecomponents in the server may support multiple reduced power states, suchas a processor, while other components may support one of two powerstates—a full power state and a low power state, or multiple powerstates that may be the same or different from the processor powerstates.

In connection with reducing the power state of the server, the host OSinstructs the IB HCA driver to put the HCA into a reduced power state,as depicted in a block 306. Before putting the HCA into the reducedpower state, the IB HCA driver or the HCA itself (e.g., via embeddedlogic) sends an “enter-low-power” power management datagram (MAD) to theSMA on the IB switch the HCA is linked to. This is also referred toherein as a power down MAD.

In a block 308, the switch's SMA records that one of its end-points(e.g., a server connected to one of its ports) is idle. The link'sPhysical Layer (PHY) transmitters and receivers for the port connectedto the idle server are then put into a “sleeping” state in accordancewith InfiniBand's link power management protocol, as described below infurther detail. The power state of the switch components that aredetected for use with the port connected to the idle server are thenreduced, also as described in further detail below.

The flowchart logic next proceeds to a decision block 310 in which adetermination is made to whether all of the nodes having HCA's linked tothe IB switch's ports are idle. If NO, the logic proceeds to end loopblock 318, whereupon it returns to start loop block 302 to begin a nextiteration of the logic. If the answer is YES, the logic proceeds to ablock 312 in which the core switch logic is put into a reduced-powerstate.

In a decision block 314 a determination is made to whether the IB switchis connected to any upstream IB switches—that is, any switches at ahigher level in the IB switch hierarchy. If YES, in a block 316 the IBswitches sends a “enter-low-power” MAD to these upstream IB switches toinform each of the upstream IB switches that it is going into areduced-power state. If the answer to decision block 314 is NO, thelogic loops back to start loop block 302 via end loop block 318, asshown.

In addition to reducing the power of components at the individual portand across the entire switch level, in one embodiment, multiple portsand associated circuitry may be powered up or down on a per-group basis.FIG. 3a shows an augmented flowchart 300 a that includes additionallogic and operations for implementing this feature. Generally, theoperations and logic in flowcharts 300 and 300 a are identical, exceptfor the addition of a decision block 311 and block 313 in flowchart 300a, as depicted with a light gray background. In decision block 311 adetermination is made to whether all of the ports in a group areoperating in a reduced-power state, such as a sleeping state defined forInfiniBand PHYs. If the answer is YES, the switch components and/orlogic for the port group is put in a reduced power state in a block 313.If some of the ports in a group are operating in a full-power state, theanswer to decision block 311 is NO, resulting in the logic proceeding toend loop block 318.

FIG. 4 shows a flowchart 400 illustrating operations and logic forreturning the power of applicable switch components and logic to anormal operating level in response to detection that an end-node hasbeen returned to a normal operation state. As delineated by start andend loop blocks 402 and 418, the operations and logic is repeatedlyperformed on an ongoing basis.

In a block 404, an end-node wakes up from a reduced-power mode. Forexample, a system management entity or the like may signal the server'sbaseboard management logic to return to a normal operating state. Inresponse, the host OS instructs the HCA driver to transition the HCA toa higher power (normal operating) state.

Previously, in accordance with block 308, the PHY components in theports at each end of the link were put into a sleeping state using theInfiniBand power management protocol. To awake the HCA port and the IBports on the opposing ends of the link and return the ports and link toa normal operating and power state, the HCA on the end-node sends a“wake” signal to the PHY on the IB switch port it is linked incommunication with, as shown in a block 406. This results in the PHYs inthe link ports and the link itself returning to a normal operating andpower state under which data may again be transmitted over the link.Additionally, the power state of the switch components dedicated for usewith the awakened port is also returned back to the normal operatingpower state. If the port is a member of a power-managed group of ports,the operating power state of the components and circuitry used tosupport operation of the group of ports is also restored to a normalstate.

Continuing at a decision block 408, a determination is made to whetherthe IB switch itself was in a reduced-power state, such as a sleepingstate. In one embodiment the port PHYs on an IB switch are configured tooperate in an autonomous manner, wherein the port PHYs themselves can bebrought back to normal operating and power state independent of theoperating and power state of other components on the IB switch,including the IB switch's core logic. Under this approach, the IB switchitself can be awoken by first waking one of the ports on the switch,such as is performed in block 406. In one embodiment, the IB switchincludes circuitry and logic to detect the operating state of each port,including when the IB switch is operating in a reduced-power state.Accordingly, upon detecting that one of its ports has returned to anormal operating state while the IB switch is in a sleeping state orsimilar reduced-power state, the answer to decision block 408 is YES,and the switch is awoken in a block 410. Awaking the switch results inreturning the core switch logic and other applicable components/logic totheir normal operating and power state. If the switch was alreadyoperating in its normal power state, the answer to decision block 408 isNO, and the logic proceeds to a block 416.

In a decision block 412, a determination is made to whether the awakenedIB switch is connected to any upstream IB switches. If the answer isYES, the applicable ports on the (downstream) IB switch and eachupstream IB switch are awoken in a manner similar to waking the linkports and PHYs in block 406. As a result, any links between the IBswitch and an upstream IB switch are returned to a normal operation andpower state in block 406.

In block 416 the switch detects that its port has returned to a normaloperating state. In response, the switch's SMA records the end-pointand/or the port has been switched back to an active state (e.g., anormal operating state). The logic then proceeds to end loop block 418,whereupon it is returned to start loop block 402 to begin a nextiteration.

FIG. 4a shows a flowchart 400 a illustrating operations and logic forreturning the power of applicable switch components and logic to anormal operating level in response to detection that an end-node hasbeen returned to a normal operating state for an IB switch having an SMAthat remains in standby mode when the IB switch is in a reduced powerstate. In this case, the SMA can receive explicit instructions and/orinformation via one or more MADs to cause reconfiguration of the IBswitch. Generally, the operations and logic for blocks in flowcharts 400and 400 a having the same reference numbers are similar. Flowchart 400 aincludes additional block 407 and 417, and doesn't include block 416.

Following the operations of block 406, in block 407 the HCA driver orHCA itself sends a “power-up” MAD to the standby SMA via the port thatwas awakened in block 406. The SMA records the end-point and/or port hasswitched back to an active state. As with flowchart 400, a determinationis made to whether the IB switch is operating in a sleeping state orsimilar reduced-power state. If so (YES), the logic proceeds to a block410 a in which the switch is awaken by the SMA. In response, the coreswitch logic and other applicable circuitry and logic is returned to anormal operating and power state.

If the IB switch is connected to one or more upstream switches, asdetermined by decision block 412, the applicable ports and associatedcircuitry are awakened in block 414 in a similar manner to thatdescribed above for flowchart 400. In addition, in a block 417, the IBswitch sends a “power-up” MAD to the SMA for each upstream IB switch toinform each upstream switch the IB switch is returning to a normal powerstate.

FIG. 5 shows an embodiment of a power-managed InfiniBand switch 500 thatis configured to support putting individual ports in reduced-powerstates, as well as putting the switch's core logic in a reduced-powerstate. InfiniBand switch 500 includes 24 ports 502, each including aphysical interface 504 including an input port 506 coupled to a receive(Rx) buffer 508 and an output port 510 coupled to a transmit (Tx) buffer512. Each port 502 is interconnected to memory 514 via interconnectcircuitry and logic, collectively illustrated by interconnect lines 516and a cross-bar switch 518. InfiniBand switch 500 further includespacket processing and switch logic 520, and a subnet management agent522. In the illustrated embodiment, cross-bar switch 518, memory 514 andpacket processing and switch logic 520 comprise core switch logic 524.In some embodiments, subnet management agent 522 may also be operated aspart of an IB switch's core switch logic. In addition, although depictedas being part of core switch logic, cross-bar switches and otherinterconnect circuitry may be operated in power states that are separatefrom the power states described herein for core switch logic.

During normal operations, each of ports 502 that are linked with anactive IB HCA or another IB switch will be operating in a normal powerstate and operate in accordance with an applicable InfiniBand protocol.Accordingly, physical interface 506 is configured to implement PHY layeroperations in accordance with the applicable IB protocol. In addition tothe components shown, each port 502 also includes additional circuitryand logic to implement the applicable IB protocol. In some embodiments,various packet processing operations may be performed at the portsthemselves, such as MAC (media access channel) layer operations, andpotentially some layer 3 operations.

Packet processing and switch logic 520 are used to depict applicablecircuitry and logic for implementing packet processing operations beyondwhich may be performed at ports 502 and implement switching operations.Generally, these operations will be facilitated by one or moreprocessing elements, such as a processor with one or more cores, anembedded network processor or the like, multiple processor engines,and/or other embedded logic. The processing elements may generallyexecute software and/or firmware instructions configured to implementpacket processing and switch operations. Generally, such software and/orfirmware may be stored in non-volatile storage on the switch itself, ormay be downloaded over a network in conjunction with initializing switchoperations.

During initialization operations and/or ongoing operations, packetprocessing and switch logic 520 will allocate various portions of memory514 for corresponding buffers or queues, as depicted by Rx queues 526and 528 and Tx queues 530 and 532. The illustrated queues are abstractedfor convenience and clarity; in a typical implementation, each activeport will generally be allocated at least one receive and transmitqueue, and may implement multiple receive and transmit queues fordifferent traffic classes. Optionally, queues for a given traffic classmay be shared across ports.

Subnet management agent 522 is configured to implement various SMAoperations discussed herein. In some embodiments, SMA 522 comprisesstandalone circuitry and logic, such as a microcontroller or low-powersingle core processor. In other embodiments, SMA 522 is implemented viasoftware and/or firmware instructions executed on a processor core orother processing element that is part of a processor or other processingelement used to implement packet processing and switch logic 520. Inthis latter case, SMA 522 will generally be part of core switch logic524 from a power-management standpoint. In one embodiment, a multi-coreprocessor dedicates one of its cores to support standby operations,wherein that core remains in a normal operating state, while other coresmay be selectively put in reduced power states.

FIG. 5a illustrates an example of InfiniBand switch 500 reducing powerat a single port in response to detecting a host server connected to theport has gone idle. For illustrative purposes, each of ports 1-5, 13-17,and 24 are shown connected to an HCA 534; however, it is noted that someports may not be connected to a host server or other end-node, and suchports may be selectively disabled. Each of HCAs 534 is installed in orotherwise operatively coupled to a host server (not shown). In thisexample, the host server having its HCA linked to port 3 has switchedoperation to a reduced-power state under which its associated HCA hasbeen put into a sleeping state in accordance with the InfiniBand powermanagement protocol. Prior to entering the sleeping state, the hostserver HCA driver or HCA itself sends a “enter-low-power” MAD to SMA522, as discussed above in block 306 of flowchart 300 in FIG. 3. Inresponse, the HCA and port 3 exchange control input MADs to enter“sleeping” state, which puts the physical interface for port 3 into theIB sleeping state. In response to detection of the physical interfaceentering the sleeping state and/or in conjunction with a control inputfrom SMA 522, the circuitry and logic dedicated for port 3 is put into areduced-power state, as depicted by the of a light gray background forport 3.

FIG. 5b illustrates an example of SMA 522 putting all of the ports 502and core switch logic 524 of InfiniBand switch 500 into a reduced powerstate upon detection that all of the host servers connected to the ports502 via their respective HCAs are in either a reduced power state ortaken offline entirely. This corresponds to the operations and logicdepicted in decision block 310 and block 312 of flowchart 300. Inconjunction with these operations, InfiniBand switch 500 sends an“enter-low-power” MAD to an upstream IB switch 536 via port 12 inaccordance with block 316 of flowchart 300. Following this, the physicalinterface of port 12 is put into an IB sleeping state, and the dedicatedcircuitry and logic for port 12 is put in a reduced-power state.

FIG. 5c shows the result of the host server for HCA 4 returning to anormal operating state. As discussed above, in one embodiment theoperation and logic of flowchart 400 of FIG. 4 is implemented forreturning HCAs and IB switch components from reduced-power and sleepingstates to normal operating and power states. Accordingly, in response toHCA 4's host server returning to its normal operating state, the PHYsfor HCA 4 and port 4 are returned from their sleeping states to a normalpower state, as described above for block 406. In accordance withdecision block 408 and block 410, powering up of port 4 is detected bySMA 522, resulting in core switch logic 524 being returned to a normaloperating and power state. In addition, the PHYs and the link betweenport 12 and IB switch 536 is returned from their sleeping state to anormal operating state in accordance with decision block 412 and block414. In block 416, SMA 522 records that the host server for HCA 4 hasswitched back to an active state.

FIG. 6 shows an InfiniBand switch 600 under which power management of IBports is on a group-wise basis. InfiniBand switch 600 includes fourmulti-port IB interfaces 602, labeled 602-1, 602-2, 602-3, and 602-4,each having 12 ports for a total of 48 ports. It is noted that thisconfiguration is merely exemplary, as the number of ports in a groupgenerally may be two or greater, and the total number of ports maygenerally range from 6-96 although this is not limiting. As shown formulti-port IB interface 602-4, each multi-port IB interface 602 includesan IB physical interface 604 including a plurality of ports 606, eachincluding an input port 607 and an output port 608 and (optionally)associated input and output port buffers (not shown for clarity). Forsimplicity, a single block for IB physical interface 604 is shown;however, it will be understood that each port 606 may have its own IBphysical interface that is operated independent for the other ports.

A cross-bar switch 610 is configured to selectively couple input andoutput port buffers (as applicable) to local memory 612, which isdepicted as including four queues including an outer receive queue 614,an outer transmit queue 616, an inner receive queue 618, and an innertransmit queue 620. Under this configuration, the outer queues are usedfor data that is received at a given multi-port IB interface that is tobe forwarded back out the same multi-port IB interface. The inner queuesare used for data that is forwarded out a different multi-port IBinterface than used to receive the data. It is noted that this is merelyexemplary, as various types of queue configurations may be implementedin local memory 612. As before, there may generally be one or morequeues for each port, and there may different queues to support multipletraffic classes, either on an individual port basis, shared port basis,or a combination thereof.

Each multi-port IB interface 602 further includes packet processing andswitch logic 622, which is generally used to perform aspects of packetprocessing and (optionally) switch operations that are performed at thelocal multi-port level rather than across the IB switch as a whole.Depending on the particularly implementation, the operations performedby packet processing and switch logic 622 may be fairly similar to theoperations performed by a single port, such as discussed above forInfiniBand switch 500, or they could be more complex, ranging all theway up to similar operations performed by packet processing and switchlogic 520 for InfiniBand switch 500 discussed above. The processingfacilities for implementing packet processing and switch logic 622 mayalso vary, depending on the complexity of the operations and/or speedthe operations are to be performed. For example, the processingfacilities may range from a microcontroller or the like to a multi-coreprocessor. Additionally, all or a portion of the packet processingoperations may be implemented by embedded hardware logic.

Each multi-port IB interface 602 may also include a power managementagent 623, or optionally, power management logic that performs similaroperations may be implemented as part of core switch logic 624, and suchpower management agent 623 is implemented as a power managementinterface configured to communicate with a power management entity incore logic 624 (not shown) and/or a subnet management agent 632. In oneembodiment, the power state of the circuitry on each multi-port IBinterface 602 exclusive to the PHYs is managed by its power managementagent 623 in cooperation with SMA 632. Optionally, each port may includeits own power management logic and operate in a substantially autonomousmanner.

In addition to SMA 632, core switch logic 624 includes a cross-barswitch 626, memory 628, and packet processing and switch logic 630.Optionally, SMA 632 may operate in a separate power domain than coreswitch logic 624 (e.g., SMA 632 is always provided with at least standbypower in one embodiment), in which case SMA 632 is not part of coreswitch logic 624.

Generally, packet processing and switch logic 630 performs operationsthat are similar to packet processing and switch logic 520 of InfiniBandswitch 500. It is also possible to split the packet processing andswitch operations between packet processing and switch logic 622 andpacket processing and switch logic 630, such as having the formerperform packet processing below the application layer, and have thelatter perform packet processing at the application layer and above, asapplicable. In connection with the packet processing and switchoperations, packet processing and switch logic 630 is configured toallocate a plurality of receive queues 634 and transmit queues 636 inmemory 628.

FIG. 6 also show various HCAs 534 connected to respective ports on themulti-port IB interfaces 602. In order to not further obscure FIG. 6with additional port identification nomenclature, each port may bereferenced by the HCA number for the HCA connected to that port, e.g.,port 1 is connected to HCA 1, port 2 is connected to HCA 2, etc.

FIG. 6 shows an initial configuration under which the host servers forall HCAs 534 are operating in normal power states. Accordingly, each ofports 606 is operating in its normal power state. As shown in FIG. 6a ,the host servers for HCAs 1, 3, 38, 40, and 41 are either in areduced-power state or offline. Accordingly, the PHYs for each of ports1, 3, 38, 40, and 41 is put into a sleeping state per the IB powermanagement protocol and dedicated circuitry for each of ports 1, 3, 38,40, and 41 is put in a reduced power state, while the remainingcircuitry in each of multi-port IB interfaces 602-1 and 602-4 remains inthe normal power state. As discussed above, the power state of thededicated circuitry for each port may be managed by power managementagent 623, or the power-state of the port circuitry may be managed bythe port itself.

As shown in FIG. 6b , at this point the host server for HCA 4 and thehost servers for HCAs 37-48 are in a reduced-power or offline state.Since there are ports in multi-port IB interface 602-1 still active, thePHY for port 4 is put into a sleeping state and the dedicated circuitryfor port 4 is put in a reduced-power state. Meanwhile, since all of theports for multi-port IB interface 602-4 are connected to host serversthat are either in a reduced power state or offline, multi-port IBinterface 602-4 is transitioned to a reduced-power state (in conjunctionwith ports 37-48 put into a sleeping state). In the illustratedembodiment, power management agent 623 remains in a standby power state.

In FIG. 6c , all of the host servers connected to InfiniBand switch 600are either in a reduced-power state or offline. In response to detectingthis situation, each of multi-port IB interfaces 602-1, 602-2, 602-3,and 602-4, and core switch logic 624 is put in a reduced-power state. Asdepicted, subnet management agent 632 is put into a standby power state.In addition, as described above in decision block 314 and block 316 offlowchart 300 a, a power down MAD indicating the IB switch 600 will beentering a reduced-power state such as a “enter-low-power” MAD is sentto IB switch 638, and the PHYs of the ports connecting IB switch 638 toIB switch 600 are put into a sleeping state.

FIG. 6d shows the result of the host server for HCA 1 returning to anormal operating state. As before, these operations are performed inaccordance with the operation and logic of flowchart 400 of FIG. 4. Inresponse to the host server for HCA 1 returning to a normal operatingstate, the PHYs for HCA 1 and port 1 are returned from their sleepingstates to a normal power state. Powering up of port 1 is detected bypower management agent 623, resulting in the portion of multi-port IBinterface 602-1 that is shared across ports being returned to a normaloperating and power state, while leaving the components dedicated to theports connected to HCAs 2-11 in there reduced-power and/or sleepingstates. Additionally, core switch logic 624 is returned to a normaloperating and power state, and the link between IB switch 600 and IBswitch 638 is returned to an active state.

The power MADs employed by the embodiments herein are to be implementedin accordance with the IB Architecture Specification (current release1.3). Details of the IB Management Model are provided in Chapter 13 ofIB Architecture Specification Volume 1, while additional details forSubnet Management and Subnet Administration are provided in Chapters14-16. The MAD base format 700 is shown in FIG. 7, with details of thevarious fields disclosed in Volume 1, Chapter 13. Bytes 0-2 comprisesthe Common MAD header format. The Device Management MAD format 800 isshown in FIG. 8. This format is used for device management, whichincludes management of IB I/O ports and IB devices, such as HCAs. TheDevice Management MAD format employs the Common MAD header format usedby the MAD base format 700 of FIG. 7. Details of the various fields forDevice Management MAD format 800 are provided in Volume 1, Chapter 16,section 16.3. As another option, a vendor-specific MAD format may beused, as described in Chapter 16, section 16.5. It is noted that DeviceManagement MAD format 800 also may be configured to supportvendor-specific functions.

Generally, one or more management methods may be employed for deliveringthe power MADs, including device management specific management methodssuch as DevMgtSet( ), DevMgtTrap( ), and DevMgtReport( ), as well asmore general management methods such as Send( ), Trap( ) and Report( ).Responses to MADs delivered using these management methods may beprovided, but are not required (except for management methods requiringresponses). However, since MADs are delivered using the IB unreliabledatagram transport service, it will generally be good practice to atleast confirm a MAD has been received. The responses may include use ofDevMgtGetResp( ), DevMgtReportResp( ), or otherwise Send( ) or Report( )may be used for sending responses to received power MADs. The responsesmay be used for purposes such as to confirm delivery of a MAD and/orconfirm that the SMA will perform operations in accordance with a powerMAD it has received. Generally, the MADs may be LID (Local ID) routed orDirect routed in accordance with the IB Subnet Management Modelspecified in Volume 1, Chapter 14.

InfiniBand Architecture Volume 2—Physical Specifications providesdetails specifying implementation of physical aspects of IB links andinterfaces, including details relating to operations of the IB PHYsemployed by the embodiments herein. The Link Physical layer provides aninterface between the packet byte stream of upper layers and the serialbit stream(s) of the physical media. The physical media may beimplemented as 1, 4, or 12 physical lanes. The packet byte stream willbe byte striped across the available physical lanes. The byte stream oneach physical lane is encoded using the industry standard 8B/10B coding.In addition to encode and decode, the link physical layer includes linktraining and initialization logic, clock tolerance compensation logic,and receive error detecting logic.

A link coupling a pair of IB ports (e.g., an IB port on a switch and anIB port on an HCA) in communication is initialized using a link trainingsequence. The link training logic in the PHYs of both ports implement alink training state diagram 900 that includes various link states, asshown in FIG. 9. The link states include a disabled state 902, a pollingstate 904, a sleeping state 906, a configuration state 908, a LinkUpstate 910, and a recovery state 912. Each of polling state 904, sleepingstate 906, configuration state 908, and recovery state 912 are superstates composed of two or more states.

In disabled state 902, the port drives its output to quiescent levelsand does not respond to received data. In polling state 904, the porttransmits training sequences and responds to received trainingsequences. This is the default state following power on. In sleepingstate 906, the port drives its outputs to quiescent levels and respondsto received training sequences. This is a reduced-power state underwhich the link is kept “alive” to enable the link to be returned toLinkUp state 910, which may be initiated by either of the link ports.Configuration state 908 is a transient super state with both thetransmitter and receiver active, and the port is attempting to configureand transition to LinkUp state 910, which is the normal like operationstate under which the port is available for transferring packets.Recovery state 912 is entered when a port experiences loss of linksynchronization, a major error, or when a link layer error triggerserror recovery. In this super state, the port attempts to re-synchronizethe link and return it to normal operation.

Changes to port and link states may be initiated by the port on eitherend of the link using applicable control input MADs. For example, anSM.PortInfo(PortPhysicalState) MAD may be employed to initiate a linktraining sequence resulting in the PHYs of both ports (and the linkitself) to enter a sleeping state. Various other types of control inputMADS, as defined in the InfiniBand Architecture Specification, may beused to cause ports and links to enter the link training statesillustrated in link training state diagram 900.

In accordance with the principles and teachings disclosed herein,improved power management of InfiniBand switches is provided, resultingin reduced power consumption and cost savings for IB switches configuredto implement aspects of the disclosed power-management methods. Whenmultiplied across the large number of IB switches used in a typical datacenter environment, the aggregated cost savings as a result of powerusage reduction is significant.

Further aspects of the subject matter described herein are set out inthe following numbered clauses:

Clause 1. An InfiniBand switch, comprising:

a plurality of ports, each port comprising a physical interface (PHY)including an input port coupled to a receive buffer and an output portcoupled to an transmit buffer;

memory operatively coupled to the receive buffers and the transmitbuffers in the plurality of ports;

packet processing and switch logic including at least one processingelement operatively coupled to the memory; and

a subnet management agent, configured to,

receive a power down management datagram (MAD) sent from a first hostserver having a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on the InfiniBand switch, the power downMAD indicating the host server is to transition to a reduced-powerstate; and

in response to receiving the power down MAD, coordinate a powerreduction of the first port.

Clause 2. The InfiniBand switch of clause 1, wherein coordinating apower reduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responsean IB link power reduction initiated by the first IB HCA; and

reducing a power level of circuitry other than the PHY dedicated tofacilitating operation of the first port.

Clause 3. The InfiniBand switch of clause 1 or 2, wherein the subnetmanagement agent is further configured to track an operating state ofthe host servers including IB HCAs linked in communication withrespective ports on the InfiniBand switch.

Clause 4. The InfiniBand switch of clause 3, wherein the InfiniBandswitch includes core switch logic, and wherein the subnet managementagent is further configured to:

detect that all servers connected to the InfiniBand switch's ports areoperating in a reduced power state or are offline; and

in response thereto, put the core switch logic into a reduced powerstate.

Clause 5. The InfiniBand switch of clause 4, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, andwherein the subnet management agent is further configured to:

send a power down MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch is going to transitionto operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, cause the portto initiate a link power reduction under which the port's PHY is putinto a sleeping state and other circuitry dedicated for operation of theport is put in one of a reduced power state or a sleeping state.

Clause 6. The InfiniBand switch of clause 4, wherein the subnetmanagement agent is further configured to:

while the core switch logic is in a reduced power state, detect at leastone of a PHY of one of the plurality of ports has returned to a normaloperating state or a port has returned to a normal operating state; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, return a power level of the core switch logic toa normal operating state.

Clause 7. The InfiniBand switch of clause 6, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, andwherein the subnet management agent is further configured to:

for each port connected to an upstream InfiniBand switch, cause the portto initiate a link power up sequence under which the port's PHY isreturned to a normal operating state from a sleeping state and the portis returned to a normal operating state; and

send a power up MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch has returned to anormal operating state.

Clause 8. An InfiniBand switch, comprising:

a plurality of multi-port InfiniBand (IB) interfaces, each includingmultiple ports comprising a physical interface (PHY) including an inputport and an output port, each multi-port IB interface further includingat least one receive buffer and at least one transmit buffer;

memory operatively coupled to receive buffers and transmit buffers inthe plurality of multi-port IB interfaces;

packet processing and switch logic including at least one processingelement operatively coupled to the memory; and

a subnet management agent, configured to,

receive a power down management datagram (MAD) sent from a first hostserver having a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on a first multi-port IB interface, thepower down MAD indicating the host server is to transition to areduced-power state; and

in response to receiving the power down MAD, coordinate a powerreduction of the first port.

Clause 9. The InfiniBand switch of clause 8, wherein coordinating apower reduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responsean IB link power reduction operation initiated by the first IB HCA; and

reducing a power level of other circuitry dedicated to facilitatingoperation of the first port.

Clause 10. The InfiniBand switch of clause 8 or 9, wherein the subnetmanagement agent is further configured to track an operating state ofthe host servers including IB HCAs linked in communication withrespective ports on the plurality of multi-port IB interfaces.

Clause 11. The InfiniBand switch of clause 10, wherein the subnetmanagement agent is further configured to:

track an operating state of each port in a multi-port IB interface thatis connected to a IB HCA hosted by a corresponding host server;

detect, for a given multi-port IB interface, that all of the hostservers having IB HCAs connected to that multi-port IB interface areoperating in a reduced power state or are offline; and

in response to detecting that all of the host servers having IB HCAslinked with that multi-port IB interface are operating in a reducedpower state or are offline, cause the multi-port IB interface to enter areduced power state.

Clause 12. The InfiniBand switch of clause 11, wherein the subnetmanagement agent is further configured to:

detect, for a given multi-port IB interface that is operating in areduced power state, that a PHY of one of the multi-port IB interface'sports has returned to a normal operating state; and

in response to detecting the PHY of the port has returned to a normaloperating state, cause the multi-port IB interface to return to a normaloperating power state.

Clause 13. The InfiniBand switch of any of clauses 8-12, wherein theInfiniBand switch includes core switch logic, and wherein the subnetmanagement agent is further configured to:

detect that all host servers connected to the InfiniBand switch's portsvia respective IB HCAs are operating in a reduced power state or areoffline; and

in response thereto, put the core switch logic into a reduced powerstate.

Clause 14. The InfiniBand switch of clause 13, wherein at least one ofthe ports is connected to an upstream InfiniBand switch, and wherein thesubnet management agent is further configured to:

send a power down MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch is going to transitionto operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, cause the portto initiate a link power reduction under which the port's PHY is putinto a sleeping state and other circuitry dedicated for operation of theport is put in one of a reduced power state or a sleeping state.

Clause 15. The InfiniBand switch of clause 13, wherein the subnetmanagement agent is further configured to:

while the core switch logic is in a reduced power state, detect at leastone of a PHY of a port has returned to a normal operating state or aport has returned to a normal operating state; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, return a power level of the core switch logic toa normal operating state.

Clause 16. A method performed in a network environment by an InfiniBandswitch having a plurality of ports, each of at least a portion of theports comprising a physical interface (PHY) connected to a respectiveInfiniBand Host Channel Adaptor (IB HCA) installed in or operativelycoupled to a respective host server, the method comprising:

receiving a power down management datagram (MAD) sent from a first hostserver having a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on the InfiniBand switch, the power downMAD indicating the host server is to transition to a reduced-powerstate; and

in response to receiving the power down MAD, coordinating a powerreduction of the first port.

Clause 17. The method of clause 16, wherein coordinating a powerreduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responseto an IB link power reduction initiated by the first IB HCA; and

reducing a power level of other circuitry dedicated to facilitatingoperation of the first port.

Clause 18. The method of clause 16 or 17, further comprising tracking anoperating state of each of the host servers.

Clause 19. The method of clause 18, wherein the InfiniBand switchincludes core switch logic, the method further comprises:

detecting that all host servers are operating in a reduced power stateor are offline; and

in response thereto, putting the core switch logic into a reduced powerstate.

Clause 20. The method of clause 19, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, themethod further comprising:

sending a power down MAD to each upstream InfiniBand switch informingthe upstream InfiniBand switch the InfiniBand switch is going totransition to operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power reduction operation under which the portis put into a reduced power state.

Clause 21. The method of clause 19, further comprising:

while the core switch logic is in a reduced power state, detecting atleast one of a PHY of one of the plurality of ports has returned to anormal operating state or a port has returned to a normal operatingstate; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, returning a power level of the core switch logicto a normal operating state.

Clause 22. The method of clause 21, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, themethod further comprising:

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power up operation under which the port's PHY isreturned to a normal operating state from a sleeping state and the portis returned to a normal operating state; and

sending a power up MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch has returned to anormal operating state.

Clause 23. A non-transitory machine-readable storage medium, having aplurality of instructions stored thereon and configured to be executedon one or more processing elements in an InfiniBand switch having aplurality of ports, each of at least a portion of the ports comprising aphysical interface (PHY) connected to a respective InfiniBand HostChannel Adaptor (IB HCA) installed in or operatively coupled to arespective host server to enable the InfiniBand switch to perform themethods of any of clauses 16-22 when executed.

Clause 24. A method performed in a network environment by an InfiniBand(IB) switch having a plurality of multi-port IB interfaces comprising aplurality of ports, each port comprising a physical interface (PHY),wherein each of at least a portion of the ports are connected to arespective InfiniBand Host Channel Adaptor (IB HCA) installed in oroperatively coupled to a respective host server, the method comprising:

receiving a power down management datagram (MAD) sent from a first hostserver having a first IB HCA linked in communication with a first porton a first multi-port IB interface, the power down MAD indicating thehost server is to transition to a reduced-power state; and

in response to receiving the power down MAD, coordinating a powerreduction of the first port.

Clause 25. The method of clause 24, wherein coordinating a powerreduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responsean IB link power reduction operation initiated by the first IB HCA; and

reducing a power level of other circuitry dedicated to facilitatingoperation of the first port.

Clause 26. The method of clause 24 or 25, further comprising tracking anoperating state for each of the host servers.

Clause 27. The method of any of clauses 24-26, further comprising:

determining, for a given multi-port IB interface, only a single port ofthe multi-port IB interface is connected to IB HCA of a host serveroperating in a normal operating state;

receiving a power down MAD from that host server indicating the hostserver is to transition to a reduced-power state;

detecting that a PHY for the single port as entered a sleeping state orthe single port has entered a reduced power state; and

causing the multi-port IB interface to enter a reduced power state.

Clause 28. The method of clause 27, further comprising:

detecting, for a given multi-port IB interface that is operating in areduced power state, that a PHY of one of the multi-port IB interface'sports has returned to a normal operating state; and

in response to detecting the PHY of the port has returned to a normaloperating state, causing the multi-port IB interface to return to anormal operating power state.

Clause 29. The method of any of clauses 24-27, wherein the InfiniBandswitch includes core switch logic, the method further comprising:

detecting that all host servers connected to the InfiniBand switch'sports via respective IB HCAs are operating in a reduced power state orare offline; and

in response thereto, put the core switch logic into a reduced powerstate.

Clause 30. The method of clause 29, wherein at least one of the ports isconnected to an upstream InfiniBand switch, the method furthercomprising:

sending a power down MAD to each upstream InfiniBand switch informingthe upstream InfiniBand switch the InfiniBand switch is going totransition to operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power reduction operation under which the port'sPHY is put into a sleeping state.

Clause 31. The method of clause 29, further comprising:

while the core switch logic is in a reduced power state, detecting atleast one of a PHY of a port has returned to a normal operating state ora port has returned to a normal operating state; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, returning a power level of the core switch logicto a normal operating state.

Clause 32. A non-transitory machine-readable storage medium, having aplurality of instructions stored thereon and configured to be executedon one or more processing elements in an InfiniBand switch having aplurality of multi-port IB interfaces comprising a plurality of ports,each port comprising a physical interface (PHY), wherein each of atleast a portion of the ports are connected to a respective InfiniBandHost Channel Adaptor (IB HCA) installed in or operatively coupled to arespective host server to enable the InfiniBand switch to perform themethods of any of clauses 24-31 when executed.

Clause 32. An InfiniBand switch, comprising:

a plurality of ports, each port comprising a physical interface (PHY)including an input port coupled to a receive buffer and an output portcoupled to an transmit buffer;

memory operatively coupled to the receive buffers and the transmitbuffers in the plurality of ports; and

means for,

receiving a power down management datagram (MAD) sent from a first hostserver having a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on the InfiniBand switch, the power downMAD indicating the host server is to transition to a reduced-powerstate; and

in response to receiving the power down MAD, coordinating a powerreduction of the first port.

Clause 33. The InfiniBand switch of clause 32, wherein coordinating apower reduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responsean IB link power reduction initiated by the first IB HCA; and

reducing a power level of other circuitry dedicated to facilitatingoperation of the first port.

Clause 34. The InfiniBand switch of clause 32 or 33, wherein theInfiniBand switch includes core switch logic, further comprising meansfor:

tracking an operating state of the host servers including IB HCAs linkedin communication with respective ports on the InfiniBand switch;

detecting that all servers connected to the InfiniBand switch's portsare operating in a reduced power state or are offline; and

in response thereto, putting the core switch logic into a reduced powerstate.

Clause 35. The InfiniBand switch of clause 34, wherein at least one ofthe plurality of ports is connected to an upstream InfiniBand switch,further comprising means for:

sending a power down MAD to each upstream InfiniBand switch informingthe upstream InfiniBand switch the InfiniBand switch is going totransition to operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power reduction under which the port's PHY isput into a sleeping state and other circuitry dedicated for operation ofthe port is put in one of a reduced power state or a sleeping state.

Clause 36. The InfiniBand switch of clause 34, further comprising meansfor:

while the core switch logic is in a reduced power state, detecting atleast one of a PHY of one of the plurality of ports has returned to anormal operating state or a port has returned to a normal operatingstate; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, returning a power level of the core switch logicto a normal operating state.

Clause 37. The InfiniBand switch of clause 36, wherein at least one ofthe plurality of ports is connected to an upstream InfiniBand switch,further comprising means for:

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power up sequence under which the port's PHY isreturned to a normal operating state from a sleeping state and the portis returned to a normal operating state; and

sending a power up MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch has returned to anormal operating state.

Clause 38. An InfiniBand switch, comprising:

a plurality of multi-port InfiniBand (IB) interfaces, each includingmultiple ports comprising a physical interface (PHY) including an inputport and an output port, each multi-port IB interface further includingat least one receive buffer and at least one transmit buffer;

memory operatively coupled to receive buffers and transmit buffers inthe plurality of multi-port IB interfaces;

packet processing and switch logic including at least one processingelement operatively coupled to the memory; and

means for,

receiving a power down management datagram (MAD) sent from a first hostserver having a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on a first multi-port IB interface, thepower down MAD indicating the host server is to transition to areduced-power state; and

in response to receiving the power down MAD, coordinating a powerreduction of the first port.

Clause 39. The InfiniBand switch of clause 38, wherein coordinating apower reduction of the first port comprises:

enabling the PHY of the first port to enter a sleeping state in responsean IB link power reduction operation initiated by the first IB HCA; and

reducing a power level of other circuitry dedicated to facilitatingoperation of the first port.

Clause 40. The InfiniBand switch of clause 39, further comprising meansfor:

tracking an operating state of the host servers including IB HCAs linkedin communication with respective ports on the plurality of multi-port IBinterfaces

tracking an operating state of each port in a multi-port IB interfacethat is connected to a IB HCA hosted by a corresponding host server;

detecting, for a given multi-port IB interface, that all of the hostservers having IB HCAs connected to that multi-port IB interface areoperating in a reduced power state or are offline; and

in response to detecting that all of the host servers having IB HCAslinked with that multi-port IB interface are operating in a reducedpower state or are offline, causing the multi-port IB interface to entera reduced power state.

Clause 41. The InfiniBand switch of clause 40, further comprising meansfor:

detecting, for a given multi-port IB interface that is operating in areduced power state, that a PHY of one of the multi-port IB interface'sports has returned to a normal operating state; and

in response to detecting the PHY of the port has returned to a normaloperating state, causing the multi-port IB interface to return to anormal operating power state.

Clause 42. The InfiniBand switch of any of clauses 38-41, wherein theInfiniBand switch includes core switch logic, further comprising meansfor:

detecting that all host servers connected to the InfiniBand switch'sports via respective IB HCAs are operating in a reduced power state orare offline; and

in response thereto, putting the core switch logic into a reduced powerstate.

Clause 43. The InfiniBand switch of clause 42, wherein at least one ofthe ports is connected to an upstream InfiniBand switch, furthercomprising means for:

sending a power down MAD to each upstream InfiniBand switch informingthe upstream InfiniBand switch the InfiniBand switch is going totransition to operating in a reduced-power state; and

for each port connected to an upstream InfiniBand switch, causing theport to initiate a link power reduction under which the port's PHY isput into a sleeping state and other circuitry dedicated for operation ofthe port is put in one of a reduced power state or a sleeping state.

Clause 44. The InfiniBand switch of clause 42, further comprising meansfor:

while the core switch logic is in a reduced power state, detecting atleast one of a PHY of a port has returned to a normal operating state ora port has returned to a normal operating state; and

in response to detecting the PHY of a port or a port has returned to itsnormal operating state, returning a power level of the core switch logicto a normal operating state.

Clause 45. A method performed in a network environment including anInfiniBand switch having a plurality of ports, each of at least aportion of the ports comprising a physical interface (PHY) connected toa respective InfiniBand Host Channel Adaptor (IB HCA) installed in oroperatively coupled to a respective host server, the method comprising:

sending a power down management datagram (MAD) from a first host serverhaving a first InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a first port on the InfiniBand switch, the power downMAD indicating the first host server is to transition to a reduced-powerstate; and

entering a reduced power state at the first host server.

Clause 46. The method of clause 45, further comprising:

exiting the reduced power state at the first host server to return thefirst host server to a normal power operating state; and

sending a power up MAD from the first host server to the InfiniBandswitch, the power up MAD indicating the first host server will return toor has returned to a normal power operating state.

Clause 47. The method of clause 46, wherein when the first host serveris in a reduced power state the IB HCA is put in a reduced power statecausing a link between the IB HCA and the InfiniBand switch to enter asleeping state, the method further comprising:

powering up the first IB HCA;

returning the link from the sleeping state to a normal operating state;and

sending the power up MAD over the link after the link has returned tothe normal operating state.

Although some embodiments have been described in reference to particularimplementations, other implementations are possible according to someembodiments. Additionally, the arrangement and/or order of elements orother features illustrated in the drawings and/or described herein neednot be arranged in the particular way illustrated and described. Manyother arrangements are possible according to some embodiments.

In each system shown in a figure, the elements in some cases may eachhave a same reference number or a different reference number to suggestthat the elements represented could be different and/or similar.However, an element may be flexible enough to have differentimplementations and work with some or all of the systems shown ordescribed herein. The various elements shown in the figures may be thesame or different. Which one is referred to as a first element and whichis called a second element is arbitrary.

In the description and claims, the terms “coupled” and “connected,”along with their derivatives, may be used. It should be understood thatthese terms are not intended as synonyms for each other. Rather, inparticular embodiments, “connected” may be used to indicate that two ormore elements are in direct physical or electrical contact with eachother. “Coupled” may mean that two or more elements are in directphysical or electrical contact. However, “coupled” may also mean thattwo or more elements are not in direct contact with each other, but yetstill co-operate or interact with each other.

Reference in the specification to “an embodiment,” “one embodiment,”“some embodiments,” or “other embodiments” means that a particularfeature, structure, or characteristic described in connection with theembodiments is included in at least some embodiments, but notnecessarily all embodiments. The various appearances “an embodiment,”“one embodiment,” or “some embodiments” are not necessarily allreferring to the same embodiments.

Not all components, features, structures, characteristics, etc.described and illustrated herein need be included in a particularembodiment or embodiments. If the specification states a component,feature, structure, or characteristic “may”, “might”, “can” or “could”be included, for example, that particular component, feature, structure,or characteristic is not required to be included. If the specificationor claim refers to “a” or “an” element, that does not mean there is onlyone of the element. If the specification or claims refer to “anadditional” element, that does not preclude there being more than one ofthe additional element.

Various components referred to above as processes, servers, or toolsdescribed herein may be a means for performing the functions described.Each component described herein includes software or hardware, or acombination of these. Each and all components may be implemented assoftware modules, hardware modules, special-purpose hardware (e.g.,application specific hardware, ASICs, DSPs, etc.), embedded controllers,hardwired circuitry, hardware logic, etc. Software content (e.g., data,instructions, configuration) may be provided via an article ofmanufacture including a non-transitory, tangible computer or machinereadable storage medium, which provides content that representsinstructions that can be executed. The content may result in a computeror processing elements performing various functions/operations describedherein.

As discussed above, various aspects of the embodiments herein may befacilitated by corresponding software and/or firmware components andapplications, such as software running on a server or firmware executedby an embedded processor on an IB switch. Thus, embodiments of thisinvention may be used as or to support a software program, softwaremodules, firmware, and/or distributed software executed upon some formof processing core (such as the CPU of a computer, one or more cores ofa multi-core processor), a virtual machine running on a processor orcore or otherwise implemented or realized upon or within anon-transitory machine-readable storage medium. A non-transitorycomputer readable storage medium includes any mechanism that provides(i.e., stores and/or transmits) information in a form accessible by acomputer (e.g., computing device, electronic system, etc.), such asrecordable/non-recordable media (e.g., read only memory (ROM), randomaccess memory (RAM), magnetic disk storage media, optical storage media,flash memory devices, etc.). The content may be directly executable(“object” or “executable” form), source code, or difference code(“delta” or “patch” code). A computer readable non-transitory storagemedium may also include a storage or database from which content can bedownloaded. Said non-transitory computer readable medium may alsoinclude a device or product having content stored thereon at a time ofsale or delivery. Thus, delivering a device with stored content, oroffering content for download over a communication medium may beunderstood as providing an article of manufacture with such contentdescribed herein.

The above description of illustrated embodiments of the invention,including what is described in the Abstract, is not intended to beexhaustive or to limit the invention to the precise forms disclosed.While specific embodiments of, and examples for, the invention aredescribed herein for illustrative purposes, various equivalentmodifications are possible within the scope of the invention, as thoseskilled in the relevant art will recognize.

These modifications can be made to the invention in light of the abovedetailed description. The terms used in the following claims should notbe construed to limit the invention to the specific embodimentsdisclosed in the specification and the drawings. Rather, the scope ofthe invention is to be determined entirely by the following claims,which are to be construed in accordance with established doctrines ofclaim interpretation.

What is claimed is:
 1. An InfiniBand switch, comprising: a plurality ofports, each port comprising a physical interface (PHY) including aninput port coupled to a receive buffer and an output port coupled to atransmit buffer; memory operatively coupled to the receive buffers andthe transmit buffers in the plurality of ports; packet processing andswitch logic including at least one processing element operativelycoupled to the memory; and a subnet management agent, configured to, foreach of the plurality of ports on the InfiniBand switch, receive a powerdown management datagram (MAD) sent from a respective host server havinga respective InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with the port, the power down MAD received by the port andindicating the respective host server is to transition to areduced-power state; and in response to receiving the power down MAD,coordinate a power reduction of the port.
 2. The InfiniBand switch ofclaim 1, wherein coordinating a power reduction of each of the portscomprises: enabling the PHY of the port to enter a sleeping state inresponse an IB link power reduction initiated by the first IB HCA; andreducing a power level of circuitry other than the PHY dedicated tofacilitating operation of the port.
 3. The InfiniBand switch of claim 1,wherein the subnet management agent is further configured to track anoperating state of the host servers including IB HCAs linked incommunication with respective ports on the InfiniBand switch.
 4. TheInfiniBand switch of claim 3, wherein the InfiniBand switch includescore switch logic, and wherein the subnet management agent is furtherconfigured to: detect that all host servers connected to the InfiniBandswitch's ports are operating in a reduced power state or are offline;and in response thereto, put the core switch logic into a reduced powerstate.
 5. The InfiniBand switch of claim 4, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, andwherein the subnet management agent is further configured to: send apower down MAD to each upstream InfiniBand switch informing the upstreamInfiniBand switch the InfiniBand switch is going to transition tooperating in a reduced-power state; and for each port connected to anupstream InfiniBand switch, cause the port to initiate a link powerreduction under which the port's PHY is put into a sleeping state andother circuitry dedicated for operation of the port is put in one of areduced power state or a sleeping state.
 6. The InfiniBand switch ofclaim 4, wherein the subnet management agent is further configured to:while the core switch logic is in a reduced power state, detect at leastone of a PHY of one of the plurality of ports has returned to a normaloperating state or a port has returned to a normal operating state; andin response to detecting the PHY of a port or a port has returned to itsnormal operating state, return a power level of the core switch logic toa normal operating state.
 7. The InfiniBand switch of claim 6, whereinat least one of the plurality of ports is connected to an upstreamInfiniBand switch, and wherein the subnet management agent is furtherconfigured to: for each port connected to an upstream InfiniBand switch,cause the port to initiate a link power up sequence under which theport's PHY is returned to a normal operating state from a sleeping stateand the port is returned to a normal operating state; and send a powerup MAD to each upstream InfiniBand switch informing the upstreamInfiniBand switch the InfiniBand switch has returned to a normaloperating state.
 8. An InfiniBand switch, comprising: a plurality ofmulti-port InfiniBand (IB) interfaces, each including multiple portscomprising a physical interface (PHY) including an input port and anoutput port, each multi-port IB interface further including at least onereceive buffer and at least one transmit buffer; memory operativelycoupled to receive buffers and transmit buffers in the plurality ofmulti-port IB interfaces; packet processing and switch logic includingat least one processing element operatively coupled to the memory; and asubnet management agent, configured to, receive a power down managementdatagram (MAD) sent from a first host server having a first InfiniBandHost Channel Adaptor (IB HCA) linked in communication with a first porton a first multi-port IB interface, the power down MAD indicating thehost server is to transition to a reduced-power state; and in responseto receiving the power down MAD, coordinate a power reduction of thefirst port.
 9. The InfiniBand switch of claim 8, wherein coordinating apower reduction of the first port comprises: enabling the PHY of thefirst port to enter a sleeping state in response an IB link powerreduction operation initiated by the first IB HCA; and reducing a powerlevel of other circuitry dedicated to facilitating operation of thefirst port.
 10. The InfiniBand switch of claim 8, wherein the subnetmanagement agent is further configured to track an operating state ofthe host servers including IB HCAs linked in communication withrespective ports on the plurality of multi-port IB interfaces.
 11. TheInfiniBand switch of claim 10, wherein the subnet management agent isfurther configured to: track an operating state of each port in amulti-port IB interface that is connected to a IB HCA hosted by acorresponding host server; detect, for a given multi-port IB interface,that all of the host servers having IB HCAs connected to that multi-portIB interface are operating in a reduced power state or are offline; andin response to detecting that all of the host servers having IB HCAslinked with that multi-port IB interface are operating in a reducedpower state or are offline, cause the multi-port IB interface to enter areduced power state.
 12. The InfiniBand switch of claim 11, wherein thesubnet management agent is further configured to: detect, for a givenmulti-port IB interface that is operating in a reduced power state, thata PHY of one of the multi-port IB interface's ports has returned to anormal operating state; and in response to detecting the PHY of the porthas returned to a normal operating state, cause the multi-port IBinterface to return to a normal operating power state.
 13. TheInfiniBand switch of claim 8, wherein the InfiniBand switch includescore switch logic, and wherein the subnet management agent is furtherconfigured to: detect that all host servers connected to the InfiniBandswitch's ports via respective IB HCAs are operating in a reduced powerstate or are offline; and in response thereto, put the core switch logicinto a reduced power state.
 14. The InfiniBand switch of claim 13,wherein at least one of the ports is connected to an upstream InfiniBandswitch, and wherein the subnet management agent is further configuredto: send a power down MAD to each upstream InfiniBand switch informingthe upstream InfiniBand switch the InfiniBand switch is going totransition to operating in a reduced-power state; and for each portconnected to an upstream InfiniBand switch, cause the port to initiate alink power reduction under which the port's PHY is put into a sleepingstate and other circuitry dedicated for operation of the port is put inone of a reduced power state or a sleeping state.
 15. The InfiniBandswitch of claim 13, wherein the subnet management agent is furtherconfigured to: while the core switch logic is in a reduced power state,detect at least one of a PHY of a port has returned to a normaloperating state or a port has returned to a normal operating state; andin response to detecting the PHY of a port or a port has returned to itsnormal operating state, return a power level of the core switch logic toa normal operating state.
 16. A method performed in a networkenvironment including an InfiniBand switch having a plurality of ports,each of at least a portion of the ports comprising a physical interface(PHY) connected to a respective InfiniBand Host Channel Adaptor (IB HCA)installed in or operatively coupled to a respective host server, themethod comprising: receiving a first power down management datagram(MAD) sent from a first host server having a first InfiniBand HostChannel Adaptor (IB HCA) linked in communication with a first port onthe InfiniBand switch, the first power down MAD received at the firstport and indicating the first host server is to transition to areduced-power state; in response to receiving the first power down MAD,coordinating a power reduction of the first port, receiving a secondpower down management datagram (MAD) sent from a second host serverhaving a second InfiniBand Host Channel Adaptor (IB HCA) linked incommunication with a second port on the InfiniBand switch, the powerdown MAD received at the second port and indicating the second hostserver is to transition to a reduced-power state; and in response toreceiving the second power down MAD, coordinating a power reduction ofthe second port.
 17. The method of claim 16, wherein the InfiniBandswitch includes core switch logic, the method further comprises:tracking an operating state of each of the host servers; detecting thatall host servers are operating in a reduced power state or are offline;and in response thereto, putting the core switch logic into a reducedpower state.
 18. The method of claim 17, wherein at least one of theplurality of ports is connected to an upstream InfiniBand switch, themethod further comprising: sending a power down MAD to each upstreamInfiniBand switch informing the upstream InfiniBand switch theInfiniBand switch is going to transition to operating in a reduced-powerstate; and for each port connected to an upstream InfiniBand switch,causing the port to initiate a link power reduction operation underwhich the port is put into a reduced power state.
 19. The method ofclaim 17, further comprising: while the core switch logic is in areduced power state, detecting at least one of a PHY of one of theplurality of ports has returned to a normal operating state or a porthas returned to a normal operating state; and in response to detectingthe PHY of a port or a port has returned to its normal operating state,returning a power level of the core switch logic to a normal operatingstate.
 20. The method of claim 19, wherein at least one of the pluralityof ports is connected to an upstream InfiniBand switch, the methodfurther comprising: for each port connected to an upstream InfiniBandswitch, causing the port to initiate a link power up operation underwhich the port's PHY is returned to a normal operating state from asleeping state and the port is returned to a normal operating state; andsending a power up MAD to each upstream InfiniBand switch informing theupstream InfiniBand switch the InfiniBand switch has returned to anormal operating state.
 21. A method performed in a network environmentincluding an InfiniBand (IB) switch having a plurality of multi-port IBinterfaces comprising a plurality of ports, each port comprising aphysical interface (PHY), wherein each of at least a portion of theports are connected to a respective InfiniBand Host Channel Adaptor (IBHCA) installed in or operatively coupled to a respective host server,the method comprising: receiving a power down management datagram (MAD)sent from a first host server having a first IB HCA linked incommunication with a first port on a first multi-port IB interface, thepower down MAD indicating the host server is to transition to areduced-power state; and in response to receiving the power down MAD,coordinating a power reduction of the first port.
 22. The method ofclaim 21, further comprising: determining, for a given multi-port IBinterface, only a single port of the multi-port IB interface isconnected to IB HCA of a host server operating in a normal operatingstate; receiving a power down MAD from that host server indicating thehost server is to transition to a reduced-power state; detecting that aPHY for the single port as entered a sleeping state or the single porthas entered a reduced power state; and causing the multi-port IBinterface to enter a reduced power state.
 23. The method of claim 22,further comprising: detecting, for a given multi-port IB interface thatis operating in a reduced power state, that a PHY of one of themulti-port IB interface's ports has returned to a normal operatingstate; and in response to detecting the PHY of the port has returned toa normal operating state, causing the multi-port IB interface to returnto a normal operating power state.
 24. The method of claim 22, whereinthe InfiniB and switch includes core switch logic, the method furthercomprising: detecting that all host servers connected to the InfiniBandswitch's ports via respective IB HCAs are operating in a reduced powerstate or are offline; and in response thereto, put the core switch logicinto a reduced power state.
 25. The method of claim 24, furthercomprising: while the core switch logic is in a reduced power state,detecting at least one of a PHY of a port has returned to a normaloperating state or a port has returned to a normal operating state; andin response to detecting the PHY of a port or a port has returned to itsnormal operating state, returning a power level of the core switch logicto a normal operating state.